Hráč 1999 April

home *** CD-ROM | disk | FTP | other *** search

/ Hráč 1999 April / Hrac_28_1999-04_cd.bin / Demos / Turok 2 / turok2demo.exe / ReadMe.txt < prev next >

Wrap

Text File | 1999-02-10 | 23.1 KB | 560 lines

*********************************************************** NOTE: Please check www.turok.com for patches and upgrades. We will continue to work at making Turok 2 a great gaming experience. *********************************************************** *********************************************************** The readme text below refers to the full retail version. This demo has been reduced in size for easier download, so references to drive space required, etc. will not reflect reality for this demo. NOTE: Unlike the full retail version, a demo server requires more info be exchanged with GameSpy Master Servers. The end result of this is that it may take as long as 5 minutes after hosting a game for your game to be listed on a GameSpy Master Server for others to join. *********************************************************** Turok 2: Seeds of Evil Contents -------- IF YOU DON'T READ ANYTHING ELSE, READ THIS Supported chipsets Minimum CPU speeds Online manual Video card drivers must be installed DirectX 6.1 (or later) must be installed Drive space Turn off other applications Turning music volume off may improve performance Command line options Strafe Modifier and Look modifer toggle keys Y Axis Looking 11 KHz, 22 KHz, and Mono options Quitting Turok 2 Wait for VRetrace Direct3D initialization errors 3Dfx VXD error Glide 3x.dll not found ComCtl32 Running Turok 2 on a 3Dfx Voodoo or Voodoo 2 card 3Dfx Banshee S3 Savage Permedia 2 based video cards How to Start a Turok2 Dedicated Server (ISPs take note) Known Microsoft Timer Bug Pen and Ink Mode IF YOU DON'T READ ANYTHING ELSE, READ THIS ------------------------------------------ You may experience difficulties running Turok 2 if you don't have the latest drivers from the manufacturer of your 3D accelerator card. Drivers were being changed right up to the last minute as testing with Turok 2 revealed problems with various cards. Typically, the chipset makers expect you to go to your card manufacturer for the latest drivers for their card. Although the chipset makers supply the 3D chip and driver software to card manufacturers, the manufacturer may tailor the driver to their particular board configuration, so the safest place to go for drivers for your board is the card manufacturer. In some cases, however, the chip maker also manufacturers the board. The following is list of web site addresses from which you can obtain the latest drivers. Also, www.turok.com will contain an updated list. If Turok 2 has problems running under the drivers you installed with your card, contact your card manufacturer for the latest version. ATI Technologies www.atitech.ca Canopus www.canopuscorp.com Creative Labs www.creaf.com Deltron Technology www.deltrontech.com Diamond Mulitmedia www.diamondmm.com Elsa www.elsa.com Hercules www.hercules.com Intergraph Computer Sys www.intergraph.com Jazz Multimedia www.jazzmm.com Leadtek www.leadtek.com Matrox www.matrox.com miro Computer products www.miro.de Number Nine, www.nine.com Orchid Technology www.orchid.com Sierra On-line www.sierra.com/hardware/ STB Systems www.stb.com TechWorks www.techworks.com Video Logic www.videologic.com Supported chipsets ------------------ Usually, but not always, if a board is based on one of the following chipsets, Turok 2 will run on it. 3Dfx Interactive Voodoo 2 3Dfx Interactive Voodoo Banshee 3Dfx Interactive Voodoo Graphics Intel 1740 Permedia 1000NT ATI Technologies 3D Rage Pro ATI Technologies Rage 128 NEC Electronics PowerVR PCX2 Nvidia Riva TNT Nvidia Riva 128 S3 Savage Rendition Verite v2100 Rendition Verite v2200 Matrox G100/G200 Minimum CPU speeds ------------------ With a 3Dfx Voodoo or equivalent, P200. 3Dfx Voodoo 2 or equivalent, P166. Online manual ------------- A complete manual for Turok 2 can be accessed as a Windows Help file directly from the Turok 2 as accessed from Windows Start Menu, or from the Turok 2 folder that will be installed on your desktop. Also, the Game Launcher's Main Menu will offer a Help selection that will take you to the help file. You can find details not listed in the manual there. Video card drivers must be installed ------------------------------------ Drivers for your 3D graphics card must be installed prior to running Turok 2. You typically do this when you first install the card. If you haven't installed the drivers, a message to the effect that no hardware accelerator cards or drivers were found will appear when you start Turok 2. DirectX 6.1 (or later) must be installed ---------------------------------------- Direct X 6.1 is installed as a normal part of the Turok 2 installation process. Drive space ----------- Turok 2 requires about 200 MB of hard drive space for a complete installation. In addition, during gameplay, Turok 2 requests 45 MB of virtual memory from Windows. Depending upon how much RAM you have, Windows may need to increase the size of your swap file to accommodate this request (this usually happens automatically). If this results in not enough disc space, Turok 2 will let you know with a message. If you have another drive or partition with 200 MB free space, you could try installing Turok 2 there instead of the default location on C: (where your swap file probably is). This will free up space on C:, allowing your swap file to grow larger, and, hopefully, Turok 2 to run. Turn off other applications --------------------------- Other Windows applications left running while playing Turok could be using system resources that would improve Turok's performance. Turning music volume off may improve performance ------------------------------------------------ Turok 2 reads music (not sound effects) from the CD during gameplay. Each time the music changes (not very often), the game may pause for a bit while the CD seeks to the new music. Setting music volume to its lowest setting will prevent this. You'll still have sound effects. Command line options -------------------- -output11k -output22k -output44k Although you can select 11Khz or 22Khz samples in the game menu, by default all sounds will mix into a 44Khz output buffer. Depending on your sound card, changing the output buffer's frequency (especially if it matches the selected sample's frequency) may speed up the sound mixing. -disableambientsounds Turns off ambient sounds (animal noises). Could improve performance on slower machines. Strafe Modifier and Look modifer toggle keys -------------------------------------------- On the joystick/pad and mouse setup screens, you can set the Y Axis Behavior (forward/backward movement of the stick or mouse) to either cause Turok 2 to look up/down or move forward/backward. You can temporarily swap these behaviors by pressing and holding the Look Modifier Toggle key on the keyboard while moving the controller in the Y axis direction. E.g., if the controller's Y axis movement normally moves Turok forward/backward, he will temporarily look up/down if this key is being depressed. The same approach applies to X Axis Behavior (side-to-side movement of the stick or mouse) which can be set to rotate or strafe. Pressing and holding the Strafe Modifier Toggle key on the keyboard while moving the controller in the X axis direction will temporarily swap behavior. Y Axis Looking -------------- In Setup for joysticks and mice, there is a Y Axis Looking option. This changes how Turok 2 looks up/down when directed by joystick/mouse movement in the Y axis (and there are two ways Y axis movement can cause Turok 2 to look up/down: either the Y Axis Behavior has been set to look up/down, or the Y axis toggle key, mentioned above, is causing Y axis movement to look up/down). If "forward looks up" is checked, Y axis movement in the forward direction will cause Turok 2 to look up. If "forward looks down" is checked, Y axis movement in the forward direction will cause Turok 2 to look down. 11 KHz, 22 KHz, and Mono options -------------------------------- Under Audio in the setup screen (click on Sample Frequency), you can choose from sounds sampled at either 11 KHz (good) or 22 KHz (better). Default is 22 KHz. Depending on your total system configuration, using one of the 11 KHz sounds may result in faster performance. Try 11 KHz and choose. Selecting Mono may also improve performance. As with all options, they will be saved for future games. Quitting Turok 2 ---------------- You can quit Turok 2 at any point by pausing and returning to Windows via the Turok 2 menu system, or by pressing Alt F4. Wait for VRetrace ------------------- An option in Video settings. Un-checking it may improve speed noticeably, but you may see screen "tearing" occasionally. Direct3D initialization errors ------------------------------ The process of initializing a 3D card to run under Direct3D involves many steps. These error messages are provided to help you troubleshoot in case the Direct3D initialization fails. In general, if you receive a Direct3D initialization error message, you should try to run Turok 2 again with a lower screen resolution Some Direct3D errors (especially #4, #7 and #15) result from having too little memory on your 3D accelerator card. You should try to run Turok 2 again in a lower screen resolution (lower screen resolutions use less memory on the 3D card). Errors #1 and #3 may mean that you do not have the latest version of DirectX installed (DirectX includes Direct3D). The correct version of DirectX was shipped with the Turok 2 CD-ROM; you should try to re-install Turok 2. Some errors (especially #10) may be a result of a conflict between your desktop's color palette and the color depth of the buffers that Turok 2 is trying to allocate on the 3D card. The desktop's color palette is set in the Display Properties window, available by choosing Start -> Settings -> Control Panel and then double clicking the Display icon. Choose the Settings tab of the Display Properties window and select High Color (16 bit) in the Color Palette drop down menu. Changing this setting may require you to restart your computer. You might also try running Turok 2 in a different screen resolution. Here are the Direct3D Initialization errors follow. NOTE: (#) represents an error code that will be returned that may help in trouble-shooting. 1. DirectDrawCreate failed. Turok 2 requires DirectDraw to run. 2. SetCooperativeLevel failed (#). Could not set DirectDraw into exclusive mode. 3. QueryInterface failed (#). Turok 2 requires DirectX 5.0 to run. 4. SetDisplayMode failed (#). Could not switch to requested screen resolution. 5. CreateSurface failed (#). Could not allocate frame buffer from 3D hardware RAM. 6. GetAttachedSurface failed (#). Could not allocate frame buffer from 3D hardware RAM. 7. Z-buffer creation failed. 3D hardware does not support 16-bit z-buffer. 8. Z-buffer allocation failed (#). Could not allocate z-buffer from 3D hardware RAM. 9. AddAttachedSurface failed (#). Could not attach z-buffer to frame buffers. 10. CreateDevice failed (#). Could not create Direct3D device data structure. 11. CreateViewport failed (#). Could not create Direct3D viewport data structure. 12. AddViewport failed (#). Could not attach Direct3D viewport data structure to Direct3D device. 13. SetViewport2 failed (#). Could not set viewport registers. 14. SetCurrentViewport failed (#). Could not set the current viewport. 15. Insufficient texture memory (# bytes) was detected to run Turok 2. The reported code number in many errors may be useful if you need to call technical support. 3Dfx VXD error -------------- While running Turok 2 on a 3Dfx-based PC, you may receive an error message something like "VXD Version 1.x searched, found 1.x". This is not a problem, simply continue with the install. You shouldn't see the error message again after the install. Glide 3x.dll not found ---------------------- While running Turok 2, if you get this message you haven't installed Glide drivers for your 3Dfx card. Get the latest (Glide 3.0 or later) and install. ComCtl32 -------- This program will be installed prior to DirectX if needed. If the ComCtl32 installation process returns a message asking if you want to re-boot, DON'T. Just continue on with the install process through DirectX installation. DirectX may ask you to re-boot, and you should do so. If DirectX doesn't ask you to re-boot, but ComCtl32 did, finish the install process and then re-boot (to finalize the ComCtl32 process). Running Turok 2 on a 3Dfx Voodoo or Voodoo 2 card ------------------------------------------------- You can use 3Dfx chip-based video cards with Turok2 in one of two ways: via 3Dfx's native "Glide" mode or via D3D. The "Glide" version is generally better and faster. However, Turok2 requires the newest version of Glide - Glide 3.0. If you have not installed Glide 3.0, and you have a Voodoo 2 card, you can run Turok 2 under D3D. Turok 2 on a Voodoo card, however, may not run well under D3D (depending on how old your drivers are). If this is the case with your card and drivers, you'll need to install and run under Glide 3.0. For your convenience, we have included Glide 3.0 on the Turok 2 CD in the "Voodoo" folder. It's contained within a self-extracting ZIP file, "RkVG.exe". Double-click on this file to extract the Glide 3.0 drivers. The default destination will be "C:\temp". If you'd rather extract to another destination, you can specify it at this point. If you want to extract to a directory that doesn't yet exist, create that directory before double-clicking on the file. Leave both check boxes checked, and click on "Unzip". The Glide drivers will be extracted to the destination directory, and Notepad will open up a readme.txt file that explains how to complete the installation. Instructions start at the top of page 2 in the "Existing Drivers ..." section. 3Dfx Banshee ------------ As we went to press 3Dfx did NOT have a Glide 3 driver for the Banshee-based cards available to the public that worked with Turok2. 3Dfx promised that a driver that did work with Turok2 would be available shortly. Typically, a Banshee board will fail by falling back to the Windows desktop just as the game begins. If this happens with your Banshee board, you can run under D3D or visit www.3dfx.com to see if they have released their fixed Glide 3 drivers to the public. 3dfx currently estimates the fixed drivers should be there on or about Feb. 9, 1999. S3 Savage --------- As we went to press there were some minor problems with the Savage and the latest drivers available to us: on the title and intro screens there is a line down the middle of the screen. Also, fires and similar objects have a line above them. We recommend getting the latest drivers for your S3-Savage based video card for potential fixes to these problems. Permedia 2 based video cards ---------------------------- There have been some reports of problems alt-tabbing back to the windows desktop and then back into the game again. Also, earlier drivers for these cards had a problem displaying transparency correctly. If your Permedia 2-based card is exhibiting either of these problems get the latest drivers from your card manufacturer. If you have problems alt-tabbing, we suggest you don't use alt-tab. How to Start a Turok2 Dedicated Server (ISPs take note) ------------------------------------------------------- If you are a retail customer and want to host a game, you will normally run Turok 2 in "Integrated Server" mode. Your PC will act as "server" to handle information flow among all players who join, as well as run a game "client" (so you can play the game with everybody else). You can also run a dedicated server. Dedicated servers benefit from having the ability to handle more players than integrated server games. A dedicated server should be run on a computer by itself (i.e., no Turok2 client running). Typically, ISP's will run dedicated servers on the internet as a service to their customers who want to play multi-player Turok2. A Turok2 server consists of two executables: an Rtime server and a game manager. The Rtime server handles Internet/LAN communication between game clients. The game manager specifies the type of game being played and the rules of the game. It also reports information about the game to GameSpy master servers and is used to arbitrate the connection between a player's Turok2 client and the Rtime server when a player joins a game. Multiple games may be running on a single Rtime server. For each game running on an Rtime server, there must be a corresponding game manager running. Typically, you will run the game manager(s) on the same computer as the Rtime server. However, it is possible to run an Rtime server and a game manger on different computers (see the gm.cfg file for more information). A package containing all the servers and necessary data files is available from http://www.turok.com. There is (or will be soon) a version of the Rtime server and game manager for the following operating systems: Server Version Server Exe Game Manager Exe ================================================================= Win32 (Win95, 98, NT) rt_srv_win32.exe gm_win32.exe Sun (Solaris 5.5 or greater) rt_srv_sun gm_sun SGI (Irix 6.2 or greater) rt_srv_sgi gm_sgi Linux (RedHat 5 or greater) rt_srv_linux gm_linux There are a few other files that must be present to run a server: RT_System.txt - contains configuration information for the Rtime server. Rtserverdll.dll - required by the Win32 version of the Rtime server. gm.cfg - contains game setup and other info. To install the servers simply unzip the T2Servers.zip file into a new directory, for example, T2Servers. This zip file can be found in the \T2Servers folder on this CD. The file contain's all the necessary files to run a Turok2 server on all the different platforms: + T2Servers + | T2Servers.txt | RT_System.txt | Rtserverdll.dll | rt_srv_win32.exe | rt_srv_sgi | rt_srv_sun | rt_srv_linux (coming soon!) | gm_win32.exe | gm_sgi (coming soon!) | gm_sun (coming soon!) | gm_linux (coming soon!) | gm.cfg + data + | Arena Levels.lsm | CTF Levels.lsm | Rok Match Levels.lsm | . . . possibly other .lsm files . . . To start a Turok2 server: First, start an Rtime server: o Locate the T2Servers directory (where the T2Servers.zip file was extracted). o From the T2Servers directory, run the appropriate server executable file for the platform. And then, start a game manager: o From the T2Servers directory, run the appropriate game manager executable for the platform. Notes about the Rtime server: o Typically, the Rtime server will start running on port 12800. If for any reason this port is not suitable (for example, it is blocked by a firewall), it can be changed by editing the RT_System.txt file. Change the "port_base=" line to reflect the desired port. Also be sure to change the ServerPort key in the game manager configuration file to reflect the new server port. Notes about the game manager: o If a game other than the default specified in the gm.cfg file is desired, edit the gm.cfg file to reflect the new game type. See the gm.cfg file for more details on customizing a game. (Note that you must restart the game manager for the changes to be effective.) o The game manager can be forced to use a different configuration file than the default gm.cfg file by passing a "-config filename" on the command line. For example, if the configuration file to be used is called arena.cfg, then run it with "gm_win32.exe -config arena.cfg". o The game manager must have access to the level set to be played. Therefore, any level set that is specified in a game manager configuration file must be present in the data subdirectory of the of the working directory. For example, if you specify "LevelSet=Rok Match Levels" in the configuration file, the level set file named "Rok Match Levels.lsm" must exist in the in the data subdirectory directory. o When running multiple game managers on the same machine, each game manager must be run with a unique configuration file and a unique port (specified in the configuration file). Up to 10 game managers may be run on a single Rtime server. o If a game manager is to be run on a LAN, it is better to specify the -lan command line parameter. This will enable a higher bandwidth version of the game. This option should NEVER be used for a game that will be played over a modem (it will saturate the modem's bandwidth and the game will be unplayable). o If the game manager exits prematurely, you may refer to the log file for diagnostic information. The log file name will be the same as the configuration file name with a .log extension instead of a .cfg extension. For example, if the configuration file used was arena.cfg, then the log file will be called arena.log. General notes: o On Unix platforms, file names are case sensitive, so be careful to match the case when specifying a new configuration file for the game manager. o Just as there is a limit to the number of game managers that can run on a single dedicated server (10), there is a limit to the number of simultaneous players allowed on a dedicated server (regardless of how many games are running): Win32 dedicated server player limit: 24 concurrent players. Unix/Linux dedicated server player limit: 48 concurrent players. o As mentioned above, you can edit the gm.cfg file to setup a game. It will be found in the root directory containing the server executables. It is amply commented, and should be self-explanatory. o Please visit www.turok.com for the latest versions of these servers. Known Microsoft Timer Bug ------------------------- As of this writing, there is a known bug with applications that use the Windows Multimedia timers (Turok 2, and many other programs do this). Rarely, you may experience a slow down in the game. Upon exiting the game, you may notice that your Windows clock shows the wrong time. At this point, Windows has actually slowed down. You'll need to reboot to get things back on track. Microsoft has fixed this bug internally, and it should be included in the next patch to Windows 95 and 98. Visit Microsoft's Web page and look for the patch. Pen and Ink Mode ---------------- Unlike the N64 version of Turok 2, there is no Pen and Ink Mode. (NOTE: this document is included Turok 2's online help)